Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[2.1] Detect HAVE_LARGE_STACKS at compile time #12384

Merged
merged 1 commit into from
Aug 19, 2021
Merged

[2.1] Detect HAVE_LARGE_STACKS at compile time #12384

merged 1 commit into from
Aug 19, 2021

Conversation

kev009
Copy link
Contributor

@kev009 kev009 commented Jul 16, 2021 •
edited
Loading

Move HAVE_LARGE_STACKS definitions to header and set when appropriate.

Reviewed-by: Brian Behlendorf [email protected]
Reviewed-by: Allan Jude [email protected]
Reviewed-by: Alexander Motin [email protected]
Reviewed-by: Ryan Moeller [email protected]
Signed-off-by: Kevin Bowling [email protected]
Closes #12350

Motivation and Context

Description

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Checklist:

@kev009
Detect HAVE_LARGE_STACKS at compile time
7b9cc28 
Move HAVE_LARGE_STACKS definitions to header and set when appropriate.

Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Allan Jude <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Kevin Bowling <[email protected]>
Closes openzfs#12350
@mmatuska
Copy link
Contributor

mmatuska commented Jul 19, 2021 •
edited
Loading

@behlendorf @tonyhutter Will there be something like a zfs-2.1.1-staging branch or is there a different policy for 2.1?

@behlendorf
Copy link
Contributor

@mmatuska thanks for the reminder, it looks like we forgot to create it. I've gone ahead and created the zfs-2.1.1-staging branch.

@behlendorf behlendorf added the Status: Accepted Ready to integrate (reviewed, tested) label Jul 26, 2021
@kev009 kev009 changed the base branch from zfs-2.1-release to zfs-2.1.1-staging July 27, 2021 16:25
@ghost
Copy link

ghost commented Aug 3, 2021

Bump

@tonyhutter tonyhutter merged commit ec6a6e8 into openzfs:zfs-2.1.1-staging Aug 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tonyhutter tonyhutter tonyhutter approved these changes

@amotin amotin amotin approved these changes

Assignees

@tonyhutter tonyhutter

Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@kev009 @mmatuska @behlendorf @amotin @tonyhutter